Virtual disk storage techniques

ABSTRACT

This document describes techniques for storing virtual disk payload data. In an exemplary configuration, each virtual disk extent can be associated with state information that indicates whether the virtual disk extent is described by a virtual disk file. Under certain conditions the space used to describe a virtual disk extent can be reclaimed and state information can be used to determine how read and/or write operations directed to the virtual disk extent are handled. In addition to the foregoing, other techniques are described in the claims, figures, and detailed description of this document.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/046,617, filed on Mar. 11, 2011, entitled “VIRTUAL DISK STORAGETECHNIQUES,” which is hereby incorporated by reference in its entirety.

BACKGROUND

Storage virtualization technology allows for the separation of logicalstorage from physical storage. One exemplary use case for storagevirtualization is within a virtual machine. A layer of virtualizingsoftware (typically called a hypervisor or virtual machine monitor) isinstalled on a computer system and controls how virtual machinesinteract with the physical hardware. Since guest operating systems aretypically coded to exercise exclusive control over the physicalhardware, the virtualizing software can be configured to subdivideresources of the physical hardware and emulate the presence of physicalhardware within the virtual machines. Another use case for storagevirtualization is within a computer system configured to implement astorage array. In this case, physical computer systems or virtualmachines can be connected to the storage array using the iSCSI protocol,or the like.

A storage handling module can be used to emulate storage for either avirtual or physical machine. For example, a storage handling module canhandle storage IO jobs issued by a virtual or physical machine byreading and writing to one or more virtual disk files, which can be usedto describe, i.e., store, the extents of the virtual disk, i.e., acontiguous area of storage such as a block. Likewise, the storagehandling program can respond to write requests by writing bit patternsdata for the virtual disk to one or more virtual disk files and respondto read requests by reading the bit patterns stored in the one or morevirtual disk files.

SUMMARY

This document describes techniques for storing data for a virtual diskin one or more virtual disk files. In an exemplary configuration, avirtual disk extent can be associated with state information thatindicates whether the virtual disk extent is described by a virtual diskfile. Under certain conditions, the space used to describe the virtualdisk extent can be reclaimed and state information can be used todetermine how to handle subsequent read and/or write operations directedto the virtual disk extent. Reclaimed space, e.g., an extent built fromone or more ranges, can be used to describe the same or another virtualdisk extent. In addition to the foregoing, other techniques aredescribed in the claims, the detailed description, and the figures.

It can be appreciated by one of skill in the art that one or morevarious aspects of the disclosure may include but are not limited tocircuitry and/or programming for effecting the herein-referencedaspects; the circuitry and/or programming can be virtually anycombination of hardware, software, and/or firmware configured to effectthe herein-referenced aspects depending upon the design choices of thesystem designer.

The foregoing is a summary and thus contains, by necessity,simplifications, generalizations and omissions of detail. Those skilledin the art will appreciate that the summary is illustrative only and isnot intended to be in any way limiting.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a high-level block diagram of a computer system.

FIG. 2 depicts a high-level block diagram of an exemplary architecturefor a virtualizing software program.

FIG. 3 depicts a high-level block diagram of an alternative architecturefor a virtualizing software program.

FIG. 4 depicts a lower-level block diagram of a computer systemconfigured to effectuate a virtual disk.

FIG. 5A depicts a lower-level block diagram of a computer systemconfigured to effectuate a virtual disk.

FIG. 5B illustrates a lower-level block diagram of a computer systemconfigured to effectuate a virtual disk.

FIG. 6 depicts a high-level block diagram of a differencing disk.

FIG. 7 depicts a high-level illustration of the relationship between avirtual disk and a virtual disk file.

FIG. 8 depicts a high-level illustration of the relationship between avirtual disk and a virtual disk file.

FIG. 9 depicts a high-level illustration of the relationship between avirtual disk and a virtual disk file.

FIG. 10 depicts a high-level illustration of the relationship between avirtual disk and a virtual disk file.

FIG. 11 depicts an operational procedure that can be implemented in acomputer-readable storage medium and/or executed by a computer system.

FIG. 12 depicts additional operations that can be executed inconjunction with those illustrated by FIG. 11.

FIG. 13 depicts additional operations that can be executed inconjunction with those illustrated by FIG. 12.

FIG. 14 depicts an operational procedure that can be implemented in acomputer-readable storage medium and/or executed by a computer system.

FIG. 15 depicts additional operations that can be executed inconjunction with those illustrated by FIG. 14.

FIG. 16 depicts an operational procedure that can be implemented in acomputer-readable storage medium and/or executed by a computer system.

FIG. 17 depicts additional operations that can be executed inconjunction with those illustrated by FIG. 16.

DETAILED DESCRIPTION

The disclosed subject matter may use one or more computer systems. FIG.1 and the following discussion are intended to provide a brief generaldescription of a suitable computing environment in which the disclosedsubject matter may be implemented.

The term circuitry used throughout can include hardware components suchas hardware interrupt controllers, hard drives, network adaptors,graphics processors, hardware based video/audio codecs, and the firmwareused to operate such hardware. The term circuitry can also includemicroprocessors, application specific integrated circuits, andprocessors, e.g., cores of a multi-core general processing unit thatperform the reading and executing of instructions, configured byfirmware and/or software. Processor(s) can be configured by instructionsloaded from memory, e.g., RAM, ROM, firmware, and/or mass storage,embodying logic operable to configure the processor to perform afunction(s). In an example embodiment, where circuitry includes acombination of hardware and software, an implementer may write sourcecode embodying logic that is subsequently compiled into machine readablecode that can be executed by hardware. Since one skilled in the art canappreciate that the state of the rut has evolved to a point where thereis little difference between hardware implemented functions or softwareimplemented functions, the selection of hardware versus software toeffectuate herein described functions is merely a design choice. Putanother way, since one of skill in the art can appreciate that asoftware process can be transformed into an equivalent hardwarestructure, and a hardware structure can itself be transformed into anequivalent software process, the selection of a hardware implementationversus a software implementation is left to an implementer.

Referring now to FIG. 1, an exemplary computing system 100 is depicted.Computer system 100 can include processor 102, e.g., an execution core.While one processor 102 is illustrated, in other embodiments computersystem 100 may have multiple processors, e.g., multiple execution coresper processor substrate and/or multiple processor substrates that couldeach have multiple execution cores. As shown by the figure, variouscomputer-readable storage media 110 can be interconnected by one or moresystem buses which couples various system components to the processor102. The system buses may be any of several types of bus structuresincluding a memory bus or memory controller, a peripheral bus, and alocal bus using any of a variety of bus architectures. In exampleembodiments the computer-readable storage media 110 can include forexample, random access memory (RAM) 104, storage device 106, e.g.,electromechanical hard drive, solid state hard drive, etc., firmware108, e.g., FLASH RAM or ROM, and removable storage devices 118 such as,for example, CD-ROMs, floppy disks, DVDs, FLASH drives, external storagedevices, etc. It should be appreciated by those skilled in the art thatother types of computer readable storage media can be used such asmagnetic cassettes, flash memory cards, and/or digital video disks.

The computer-readable storage media 110 can provide non volatile andvolatile storage of processor executable instructions 122, datastructures, program modules and other data for the computer system 100such as executable instructions. A basic input/output system (BIOS) 120,containing the basic routines that help to transfer information betweenelements within the computer system 100, such as during start up, can bestored in firmware 108. A number of programs may be stored on firmware108, storage device 106, RAM 104, and/or removable storage devices 118,and executed by processor 102 including an operating system and/orapplication programs. In exemplary embodiments, computer-readablestorage media 110 can store virtual disk parser 404, which is describedin more detail in the following paragraphs, can be executed by processor102 thereby transforming computer system 100 into a computer systemconfigured for a specific purpose, i.e., a computer system configuredaccording to techniques described in this document.

Commands and information may be received by computer system 100 throughinput devices 116 which can include, but are not limited to, a keyboardand pointing device. Other input devices may include a microphone,joystick, game pad, scanner or the like. These and other input devicesare often connected to processor 102 through a serial port interfacethat is coupled to the system bus, but may be connected by otherinterfaces, such as a parallel port, game port, or universal serial bus(USB). A display or other type of display device can also be connectedto the system bus via an interface, such as a video adapter which can bepart of, or connected to, a graphics processor unit 112. In addition tothe display, computers typically include other peripheral outputdevices, such as speakers and printers (not shown). The exemplary systemof FIG. 1 can also include a host adapter, Small Computer SystemInterface (SCSI) bus, and an external storage device connected to theSCSI bus.

Computer system 100 may operate in a networked environment using logicalconnections to one or more remote computers, such as a remote computer.The remote computer may be another computer, a server, a router, anetwork PC, a peer device or other common network node, and typicallycan include many or all of the elements described above relative tocomputer system 100.

When used in a LAN or WAN networking environment, computer system 100can be connected to the LAN or WAN through network interface card 114.The NIC 114, which may be internal or external, can be connected to thesystem bus. In a networked environment, program modules depictedrelative to the computer system 100, or portions thereof, may be storedin the remote memory storage device. It will be appreciated that thenetwork connections described here are exemplary and other means ofestablishing a communications link between the computers may be used.Moreover, while it is envisioned that numerous embodiments of thepresent disclosure are particularly well-suited for computerizedsystems, nothing in this document is intended to limit the disclosure tosuch embodiments.

Turning to FIG. 2, illustrated is an exemplary virtualization platformthat can be used to generate virtual machines. In this embodiment,microkernel hypervisor 202 can be configured to control and arbitrateaccess to the hardware of computer system 200. Microkernel hypervisor202 can generate execution environments called partitions such as childpartition 1 through child partition N (where N is an integer greaterthan 1). Here, a child partition is the basic unit of isolationsupported by microkernel hypervisor 202. Microkernel hypervisor 202 canisolate processes in one partition from accessing another partition'sresources. In particular, microkernel hypervisor 202 can isolate kernelmode code of a guest operating system from accessing another partition'sresources as well as user mode processes. Each child partition can bemapped to a set of hardware resources, e.g., memory, devices, processorcycles, etc., that is under control of the microkernel hypervisor 202.In embodiments, microkernel hypervisor 202 can be a stand-alone softwareproduct, a part of an operating system, embedded within firmware of themotherboard, specialized integrated circuits, or a combination thereof.

Microkernel hypervisor 202 can enforce partitioning by restricting aguest operating system's view of the memory in a physical computersystem. When microkernel hypervisor 202 instantiates a virtual machine,it can allocate pages, e.g., fixed length blocks of memory with startingand ending addresses, of system physical memory (SPM) to the virtualmachine as guest physical memory (GPM). Here, the guest's restrictedview of system memory is controlled by microkernel hypervisor 202. Theterm guest physical memory is a shorthand way of describing a page ofmemory from the viewpoint of a virtual machine and the term systemphysical memory is shorthand way of describing a page of memory from theviewpoint of the physical system. Thus, a page of memory allocated to avirtual machine will have a guest physical address (the address used bythe virtual machine) and a system physical address (the actual addressof the page).

A guest operating system may virtualize guest physical memory. Virtualmemory is a management technique that allows an operating system to overcommit memory and to give an application sole access to a logicallycontiguous working memory. In a virtualized environment, a guestoperating system can use one or more page tables, called guest pagetables in this context, to translate virtual addresses, known as virtualguest addresses into guest physical addresses. In this example, a memoryaddress may have a guest virtual address, a guest physical address, anda system physical address.

In the depicted example, parent partition component, which can also bealso thought of as similar to domain 0 of Xen's open source hypervisorcan include a host environment 204. Host environment 204 can be anoperating system (or a set of configuration utilities) and hostenvironment 204 can be configured to provide resources to guestoperating systems executing in the child partitions 1-N by usingvirtualization service providers 228 (VSPs). VSPs 228, which aretypically referred to as back-end drivers in the open source community,can be used to multiplex the interfaces to the hardware resources by wayof virtualization service clients (VSCs) (typically referred to asfront-end drivers in the open source community or paravirtualizeddevices). As shown by the figures, virtualization service clientsexecute within the context of guest operating systems. However, thesedrivers are different than the rest of the drivers in the guest in theycommunicate with host environment 204 via VSPs instead of communicatingwith hardware or emulated hardware. In an exemplary embodiment the pathused by virtualization service providers 228 to communicate withvirtualization service clients 216 and 218 can be thought of as theenlightened IO path.

As shown by the figure, emulators 234, e.g., virtualized IDE devices,virtualized video adaptors, virtualized NICs, etc., can be configured torun within host environment 204 and are attached to emulated hardwareresources, e.g., IO ports, guest physical address ranges, virtual VRAM,emulated ROM ranges, etc. available to guest operating systems 220 and222. For example, when a guest OS touches a guest virtual address mappedto a guest physical address where a register of a device would be for amemory mapped device, microkernel hypervisor 202 can intercept therequest and pass the values the guest attempted to write to anassociated emulator. Here, the emulated hardware resources in thisexample can be thought of as where a virtual device is located in guestphysical address space. The use of emulators in this way can beconsidered the emulation path. The emulation path is inefficientcompared to the enlightened IO path because it requires more CPU time toemulate devices than it does to pass messages between VSPs and VSCs. Forexample, several actions on memory mapped to registers are required inorder to write a buffer to disk via the emulation path, while this maybe reduced to a single message passed from a VSC to a VSP in theenlightened IO path, in that the drivers in the VM are designed toaccess IO services provided by the virtualization system rather thandesigned to access hardware.

Each child partition can include one or more virtual processors (230 and232) that guest operating systems (220 and 222) can manage and schedulethreads to execute thereon. Generally, the virtual processors areexecutable instructions and associated state information that provide arepresentation of a physical processor with a specific architecture. Forexample, one virtual machine may have a virtual processor havingcharacteristics of an Intel x86 processor, whereas another virtualprocessor may have the characteristics of a PowerPC processor. Thevirtual processors in this example can be mapped to processors of thecomputer system such that the instructions that effectuate the virtualprocessors will be directly executed by physical processors. Thus, in anembodiment including multiple processors, virtual processors can besimultaneously executed by processors while, for example, otherprocessor execute hypervisor instructions. The combination of virtualprocessors and memory in a partition can be considered a virtualmachine.

Guest operating systems (220 and 222) can be any operating system suchas, for example, operating systems from Microsoft®, Apple®, the opensource community, etc. The guest operating systems can includeuser/kernel modes of operation and can have kernels that can includeschedulers, memory managers, etc. Generally speaking, kernel mode caninclude an execution mode in a processor that grants access to at leastprivileged processor instructions. Each guest operating system can haveassociated file systems that can have applications stored thereon suchas terminal servers, e-commerce servers, email servers, etc., and theguest operating systems themselves. The guest operating systems canschedule threads to execute on the virtual processors and instances ofsuch applications can be effectuated.

Referring now to FIG. 3, it illustrates an alternative virtualizationplatform to that described above in FIG. 2. FIG. 3 depicts similarcomponents to those of FIG. 2; however, in this example embodimenthypervisor 302 can include a microkernel component and componentssimilar to those in host environment 204 of FIG. 2 such as thevirtualization service providers 228 and device drivers 224, whilemanagement operating system 304 may contain, for example, configurationutilities used to configure hypervisor 302. In this architecture,hypervisor 302 can perform the same or similar functions as microkernelhypervisor 202 of FIG. 2; however, in this architecture hypervisor 304effectuates the enlightened IO path and includes the drivers for thephysical hardware of the computer system. Hypervisor 302 of FIG. 3 canbe a stand alone software product, a part of an operating system,embedded within firmware of the motherboard or a portion of hypervisor302 can be effectuated by specialized integrated circuits.

Turning now to FIG. 4, it describes computer system 400, whichillustrates a high-level block diagram of components that can be used toeffect the techniques described in this document. Briefly, computersystem 400 can include components similar to those described above withrespect to FIG. 1 through 3. FIG. 4 shows virtualization system 420,which can be thought of as a high-level representation of thevirtualization platform illustrated by FIG. 2 or FIG. 3. For example,virtualization system 420 can be thought of as a high-levelrepresentation of the combination of features provided by microkernelhypervisor 202 and host environment 204. Alternatively, virtualizationsystem 420 can be thought of as a high-level representation ofhypervisor 302 and management OS 304. Thus, use of the term“virtualization system 420” throughout this document signals that thevirtual disk techniques described in the following paragraphs can beimplemented within any type or virtualization software layer or in anytype of virtualization platform.

Virtualization system 420 can include offload provider engine 42.Briefly, offload provider engine 422 can be configured to serviceoffload read and offload write requests (sometimes called PROXY READ andPROXY WRITE) issued by, for example, application 424. An offload readrequest is a request to create a token that represents data that wouldhave been read if the offload read had been a normal read. An offloadwrite is a request to write the data represented by a token to adestination location. In one usage example, an offload read followed byan offload write can be used to copy data from one location to another,e.g., from computer system 400 to a destination computer system within adomain by using tokens that represent the data to avoid moving the datathrough local RAM. For example, suppose that computer system 400 and adestination computer system (not shown) can access a common datarepository and a request to copy data from computer system to thedestination is received. Instead of copying the data to the destination,application 424 can issue a request to offload provider engine 422 toissue a token that represents the data as it exists at the time thetoken is associated with the data. The token can be sent to thedestination and used by a program running on the destination to obtainthe data from the common data storage repository and write the data tothe destination. Copy-offload techniques are described in more detail inco-pending U.S. patent application Ser. No. 12/888,433, entitled“Offload Reads and Writes” and U.S. patent application Ser. No.12/938,383, entitled “Virtualization and Offload Reads and Writes,” thecontents of which are herein incorporated by reference in their entiretyto the extent they are consistent with techniques described in thisdocument.

Virtual disk parser 404, which can be a module of executableinstructions in a specific example embodiment, can be used toinstantiate virtual disks from virtual disk files and handle storage IOon behalf of a virtual machine. As shown by the figure, virtual diskparser 404 can open one or more virtual disk files such as virtual diskfile(s) 406 and generate virtual disk 402.

Virtual disk parser 404 can obtain virtual disk file(s) 406 from storagedevice 106 via virtualization system file system 408. Briefly,virtualization system file system 408 represents a software module thatorganizes computer files and data of virtualization system 420, such asvirtual disk file(s) 406. Virtualization system file system 408 canstore this data in an array of fixed-size physical extents, i.e.,contiguous areas of storage on a physical storage device. In a specificexample, an extent can be a cluster, which is a sequence of bytes ofbits having a set length. Exemplary cluster sizes are typically a powerof 2 between 512 bytes and 64 kilobytes. In a specific configuration, acluster size can be 4 kilobytes.

When a request to open virtual disk file 406 is received, virtualizationsystem file system 408 determines where the file is located on disk andissues an IO job to the disk device driver to read the data from one ormore physical extents of the disk. The IO job issued by file system 408determines a disk offset and length that describes the location of thepersistent copy of virtual disk file 406 on storage device 106 andissues the IO job to storage device 106. Due to the semantics of howstorage devices operate, a write IO job can be buffered in one or morelevels of caches of volatile memory, represented by cache 454, until thecircuitry of storage device 106 determines to access the location on thepersistent storage unit 460, e.g., a platter, a flash memory cell, etc.,and write the buffered bit pattern indicative of the new contents of thepersistent copy of the virtual disk file(s) 406 to persistent storageunit 460.

Virtual disk parser 404 can obtain the bit pattern indicative of virtualdisk file(s) 406 and expose the payload, e.g., user data, in the virtualdisk file(s) 406 as a disk including a plurality of virtual diskextents. In an embodiment, these virtual disk extents can be afixed-size block 512 kilobytes up to 64 megabytes in size andpartitioned into a plurality of sectors; however, in another embodimentthe virtual disk extents could be variable-sized extents. In anexemplary configuration, prior to booting guest operating system 412,resources related to an emulated or enlightened storage controller andemulated or enlightened aspects of a virtual disk are setup such that anemulated storage controller with memory mapped registers is effectedwithin guest physical address space of the virtual machine 410. Bootcode can run and boot guest operating system 412. Virtualization system420 can detect an attempt to access this region of guest physicaladdress space and return a result that causes guest operating system 412to determine that a storage device is attached to the emulated storagecontroller. In response, guest operating system 412 can load a driver(either a paravirtualization driver or a regular driver) and use thedriver to issue storage IO requests to the detected storage device.Virtualization system 420 can route the storage IO requests to virtualdisk parser 404.

After guest operating system 412 is running it can issue IO jobs tovirtual disk 402 via file system 414, which is similar to virtualizationsystem file system 414 in that it organizes computer files and data ofguest operating system 412 and applications installed on guest operatingsystem 412. Guest operating system 412 can interact with virtual disk402 in a way that is similar to how an operating system interacts with aphysical storage device and eventually the IO jobs are routed to virtualdisk parser 404. Virtual disk parser 404 can include logic fordetermining how to respond to the IO jobs in a way that emulates aphysical storage device. For example, virtual disk parser 404 can readdata from virtual disk file(s) 406 and write data to virtual diskfile(s) 406. The data written to virtual disk file(s) 406 in turn isrouted through virtualization system file system 408 and committed to apersistent copy of virtual disk file(s) 406 stored on or in persistentstorage unit 460.

Referring briefly to FIG. 5A, it illustrates an alternative architecturefor implementing techniques described in this document. As shown by FIG.5, virtual disk parser 404 can also be implemented in an operatingsystem 502 such as an operating system offered by Microsoft®. In thisexample, virtual disk parser 404 can be configured to run on storageserver 500, which could include components similar to computer system100 of FIG. 1. In this example, storage server 500 could include anarray of physical storage devices 510 and can be configured to makestorage available to servers such that the storage appears as locallyattached to operating system 508. Virtual disk parser 404 can operatethe same as it was described with respect to FIG. 4; the differencebeing in this configuration read/write IO jobs issued by file system 414can be routed over a network connection to virtual disk parser 404.

Referring briefly to FIG. 5B, it illustrates yet another architecturefor implementing techniques described in this document. FIG. 5B issimilar to FIG. 5A in that virtual disk parser 404 is implemented inoperating system 502 and computer system 512 could include componentssimilar to computer system 100 of FIG. 1. The difference in thisexample; however, is that the figure illustrates a loopback-attachedvirtual disk 402. File system 414, including applications such asapplication 424 can be stored in virtual disk 402 and virtual diskfile(s) 406 can be stored in computer system file system 514.

Turning attention now to virtual disk 402, while it can be effected by asingle virtual disk file, in other configurations a group ofdifferencing virtual disk files can be used to bring about virtual disk402. FIG. 6 illustrates exemplary chains of virtual disk files that canbe used by virtual disk parser 404 to effect virtual disk 402 as adifferencing disk. Generally, a differencing virtual disk filerepresents the current state of a virtual disk as a set of modifiedextents in comparison to a parent image. The parent image can be anotherdifferencing virtual disk file or a base virtual disk file.

In an exemplary configuration, the linking between a parent virtual diskfile and a child virtual disk file can be stored within the child. Inparticular, the child can include an identifier of the parent and avalue that describes the location of the parent. When starting a virtualmachine, virtual disk parser 404 may receive information that describesthe last virtual disk file in the chain, i.e., virtual disk file 612 isthe last in a chain that includes virtual disk files 612, 610, 606, and600, and open this file. This file can include an identifier of itsparent, i.e., virtual disk file 610, and a path to it. Virtual diskparser 404 can locate and open the parent and so on and so forth until abase virtual disk file is located and opened.

Virtual disk parser 404 can use information that indicates whether datais present or stored in a parent virtual disk file. Typically, the lastvirtual disk file in the chain is opened as read/modify and othervirtual disk files arc opened as read only. Thus, writes are typicallymade to the last virtual disk file in the chain. Read operations aresimilarly directed first to the last virtual disk file in the chain andvirtual disk parser 404 will logically search the virtual disk files inlogical order from last to base until the data is found in the instancethat information about where the data is located is not cached. In aspecific example, a block allocation table (not shown) for a virtualdisk file, e.g., virtual disk file 612, can include state informationthat indicates whether the virtual disk extent is defined by a sectionof the virtual disk file or if this virtual disk extent is transparent,e.g., defined by a different virtual disk file further along the chain.In one implementation, virtual disk parser 404 can determine whetherthis virtual disk extent is transparent and access the block allocationtable for the next virtual disk file in the chain, e.g., virtual diskfile 610, and so on and so forth until a virtual disk file in the chainis located that defines the data.

Referring now to FIG. 7, it illustrates virtual disk 402 described atleast in part by virtual disk file 702, which could be similar to anyvirtual disk file described in FIG. 6 that is write/modifiable, e.g.,virtual disk file 602, 608, or 612, or a single virtual disk file. Asshown by the figure, virtual disk 402 can include N extents of storage(where N is an integer greater than 0) and in this specific examplevirtual disk 402 includes 10 extents. Virtual disk 402 is illustrated asincluding the bit patterns for different files and data for guestoperating system 412, which are differentiated by the different patternswith in the virtual disk extents.

Since virtual disk 402 is not a physical storage device, the underlyingpayload data for the virtual disk extents can be “described by,” i.e.,stored in, different sections within virtual disk file 702. For example,virtual disk extent 1 is described by a section that is defined by avirtual disk file offset value 0 or the first offset that can be used tostore payload data. Allocation table 416, which can be stored in randomaccess memory while computer system 400 is in operation, can bepersisted in virtual disk file 702 in any section and can span multiplesections. Briefly, allocation Table 416 can include information thatlinks virtual disk extents to sections of virtual disk file 702. Forexample, allocation Table 416 can store information that defines thevirtual disk file byte offsets that define the section of virtual diskfile 702 that stores the data. The arrows signify the relationshipsstored in allocation table 416.

Described in more detail in the following paragraphs, allocation table416 can also include state information; however, this configuration isexemplary. In alternate configurations this information can be stored ina different section of virtual disk file 702 and loaded into RAM 104.Allocation table 416 can include an entry for each virtual disk extent;state information indicating what state each extent is in; and a fileoffset indicating where in virtual disk file 702 each virtual diskextent is described (not illustrated). In an alternative embodiment anextent could also be defined by multiple already-mapped and contiguous(in file offset) table entries. In this configuration, reads and writesthat cross block boundaries can be serviced as a single read/write tovirtual disk file 702 if the block payloads are contiguous in the file.In a specific example, virtual disk parser 404 can also storeinformation that indicates what type of bit pattern is stored in eachunused section of the virtual disk file, i.e., a free space map. Inaddition to the foregoing, the free-space map can allow be used byvirtual disk parser 404 to determine which sectors of virtual disk file406 are used and which are free. The free space map in this example canbe configured to track free space in the file that is non-zero. In anexemplary embodiment, because using a non-zero portion of free space todescribe a portion of virtual disk 402, which must be zero or must notdisclose information from other virtual disk offsets, the free space isoverwritten with zeros or a non-information disclosing pattern(typically zeros), respectively. Virtual disk parser 404 can use thisinformation in order to determine what section of virtual disk file toallocate to a virtual disk extent. For example, if a virtual disk extentin the zero state is written to, virtual disk parser 404 can allocate asection that already has zeros in it to back the virtual disk extent.

As guest operating system 412 or operating system 508 rans it willgenerate data and files and issue disk writes to virtual disk 402 tostore data. When virtual disk file 702 does not have any additionalnon-used space, virtual disk parser 404 can extend the end of file anduse the new space to describe the virtual disk extents. Guest operatingsystem 412 or operating system 508 may use, delete, and reuse sectionsof virtual disk 402; however, since virtual disk parser 404 is merelystoring data on behalf of file system 414, virtual disk parser 404 maybe unable to determine whether a section of virtual disk file is stillbeing used by guest operating system 412. Consequently, virtual diskparser 404 may hold allocated space in virtual disk file 702 to describevirtual disk extents that are no longer in use by file system 414. Theresult of this is that the size of virtual disk file 702 may grow untilit reaches the size of virtual disk 402.

In exemplary embodiments, virtual disk parser 404 can be configured toreclaim unused sections of a virtual disk file and optionally reusethem. As such, the frequency at which the virtual disk file needs to beextended is reduced, and the overall size of the virtual disk file isreduced. In an example embodiment, when a file system signals that it isno longer using a virtual disk extent, virtual disk parser 404 cande-allocate, i.e., unlink, the virtual disk extent from the virtual diskfile and associate the virtual disk extent with information thatdescribes how read operations to the virtual disk extent should betreated. The section of the virtual disk file can then be reused todescribe the same or another virtual disk extent.

In an exemplary configuration, virtual disk parser 404 can use TRIM,UNMAP, and/or WRITE SAME of zero commands issued by a file system todetermine when a virtual disk extent can be de-allocated from virtualdisk file(s) 406. TRIM commands can be issued by guest operating system412 or operating system 508. For example, as guest operating system 412or operating system 508 runs, file system 414 may determine that somesectors are no longer needed and issue a TRIM command. Alternatively oradditionally, virtual disk parser 404 can be configured to request thatfile system 414 issue TRIM commands at predetermined intervals, or whenpredetermined criteria are satisfied, e.g., when virtual machine 410 isinstantiated, when virtual machine 410 is shut down, under light use,etc.

Briefly, a TRIM command is used to inform the data storage device as towhich sectors are no longer considered in use so that the data storedtherein can be optionally discarded by the data storage device. One typeof TRIM command, called a free space TRIM command, can be used by filesystem 414 to signal that sectors are no longer in use by file system414 and the other, called a standard TRIM command, does not. Thedifference between the two types of TRIM commands is that when a sectoris the subject of a free space TRIM, file system 414 provides securityfor the sector by preventing user space applications and the like fromreading from the sector. The fact that file system 414 secures access tosectors that have been trimmed in this way can be used to increase theability to efficiency allocate virtual disk file space. This particularaspect is described in more detail in the following paragraphs.

In an exemplary configuration, virtual disk parser 404 can be configuredto execute reclamation operations when a virtual disk extent is fullycovered by a TRIM command. Or put another way, virtual disk parser 404can unlink virtual disk extents from the virtual disk file in responseto receipt of a TRIM command that defines a range of virtual disksectors that identifies all of the sectors in the virtual disk extent.In the same or an alternative embodiment, when a TRIM command isreceived that covers a portion of a virtual disk extent, virtual diskparser 404 can determine what portion of the virtual disk filecorresponds to the trimmed sectors and send a TRIM command for theportion of the virtual disk file to storage device 106. In this example,the underlying file system, e.g., virtualization system file system 408,storage server file system 504, or computer system file system 514 cantranslate the offsets of the TRIM command and send the translatedoffsets to storage device 106, reclaim space directly via internal datastructure updates, or clear data from caches.

In the same or another embodiment, when a TRIM command is received thatcovers a portion of a virtual disk extent, virtual disk parser 404 canbe configured to store information that indicates what sectors have beenthe subject of the TRIM command and whether the TRIM command was a freespace trim or not. In the instance that the remainder of the virtualdisk extent is trimmed, virtual disk parser 404 can de-allocate thevirtual disk extent from the virtual disk file.

When de-allocating virtual disk extents, virtual disk parser 404 canassociate the virtual disk extent with state information that describeshow read operations directed to the virtual disk extent can be handled.Table 1 illustrates exemplary state information that virtual disk parser404 can associate with virtual disk extents and use to optimize thereclamation of the virtual disk file. The ability to reclaim a virtualdisk extent can he accomplished in one example by using two states(described and not described); however, since the bit pattern stored invirtual disk file 702 is not typically erased when the data is deleted,additional states can be used to determine when space selected todescribe a virtual disk extent needs to be cleared before it can bereused or if it can be reused without overwriting the data previouslystored therein. One reason for why the data is not erased upon deletionis that it costs processor cycles to erase data and since some storagedevices are configured to perform write operations on a per-block basis,it is more efficient to erase data when over-writing with new data. Thefollowing states are exemplary and the disclosure is not limited tousing states that are defined by the following table.

TABLE 1 State Description Mapped This state indicates that the virtualdisk extent is linked to the virtual disk file. Transparent This stateindicates that the virtual disk extent is defined by a different virtualdisk file. Zero This state indicates that the virtual disk extent is notdescribed by the virtual disk file. In addition, this state indicatesthat the virtual disk extent is defined as zero and that the zeros aremeaningful. Unmapped This state indicates that the virtual disk extentis not described by the virtual disk file. In an embodiment, this statecan include sub-states anchored and unanchored. Uninitialized This stateindicates that the virtual disk extent is not described by the virtualdisk file and that the virtual disk extent is defined as free space. Inan embodiment, this statement can also include sub-states anchored andunanchored.

Referring to Table 1 in conjunction with FIG. 7, the first state listedis the “mapped” state, which indicates that the virtual disk extent isdescribed by a section of virtual disk file 702. For example, virtualdisk extent 0 is an example virtual disk extent that is illustrated asbeing in the “mapped” state.

Continuing with the description of Table 1, a virtual disk extent can beassociated with state information that indicates that the virtual diskextent is “transparent,” that is, the virtual disk extent is describedby a different virtual disk file. In the instance that a read operationis received by virtual disk parser 404 to a virtual disk extent in thetransparent state, virtual disk parser 404 can refer to a differentvirtual disk file and check its allocation table to determine how torespond to the read. In an instance that virtual disk parser 404receives a write to the virtual disk extent, virtual disk parser 404 cantransition the virtual disk extent from the “transparent” state to the“mapped” state.

Continuing with the description of Table 1 in conjunction with FIG. 7, avirtual disk extent can also be associated with the “unmapped” state. Inthis example, the virtual disk extent is not described by virtual diskfile 702 nor is it described by any other virtual disk file in a chain.In this example, the unmapped state can be used to describe a virtualdisk extent that was subject to a TRIM command that did not indicatethat file system 414 would secure access to the virtual disk extent. Orput another way, the TRIM command used to transition this virtual diskextent to this state was a standard TRIM command. In the instance thatthe virtual disk extent is in the unmapped state and an IO jobindicative of a read to the extent is received, virtual disk parser 404can respond with zeros, the zero token, ones, a token representing allones, or a non-information-disclosing bit pattern, e.g., all zeros, allones, or a randomly generated pattern of ones and zeros. In thisexample, if a section of virtual disk file 702 is allocated to back avirtual disk extent in this state, virtual disk parser 404 can write anon-information disclosing bit pattern to the section of virtual diskfile 702 before allocating it or select a section that already includesa non-information disclosing bit pattern to describe the virtual diskextent. Virtual disk extent 6 of FIG. 7 is indicated as in the unmappedstate.

In an embodiment, the data defining an unmapped or uninitialized extentcan be kept and the unmapped or uninitialized state can include twosub-states: anchored, which means that the data is still present withinvirtual disk file 702, and unanchored, which means that the data may ormay not be kept. In instances where these sub-states are used, virtualdisk parser 404 can transition an unmapped but anchored extent to mappedby allocating the section or sections that store the data withoutzeroing the section or sections. Similarly, while virtual disk parser404 is configured to treat uninitialized extents as if they wereunmapped for at least a portion of virtual disk 402, virtual disk parser404 can avoid zeroing an uninitialized but anchored extent duringtransition of that extent to mapped, by allocating the section orsections that store the data without zeroing the section or sections.

Table 1 additionally describes a “zero” state. In this example, thevirtual disk extent is not described by virtual disk file 702 nor is itdescribed by any other virtual disk file in a chain; however, thevirtual disk extent is required to read as all zeros. In this example,the zero state can be used to describe a virtual disk extent that wassubject to either type of TRIM command or to describe a virtual diskextent that a program has written all zeros to. For example, suppose adeletion utility program wrote all zeros to virtual disk extent 4 toensure that the data it previously stored was completely overwritten. Inthe instance that the virtual disk extent is in the zeroed state, and anIO job indicative of a read to the extent is received, virtual diskparser 404 can respond to with zeros or the zero token (in an offloadread operation). In the instance that a \write is directed to a virtualdisk extent in this state, virtual disk parser 404 can zero a section ofvirtual disk file 702 and use it to describe the virtual disk extent orselect a section of virtual disk file 702 that is already zero andallocate it to back the virtual disk extent. In this embodiment, zeroedspace could be tracked using a data structure or virtual disk file 702.The data structure could be updated periodically, when virtual disk file702 is opened, when virtual disk file 702 is closed, etc. A read from anextent in the unmapped or uninitialized states may optionally causevirtual disk parser 404 to transition the extent to the zero state in aconfiguration where virtual disk parser 404 is configured to providesector stability for extents in the unmapped or uninitialized states.

Table 1 also describes a state called the “uninitialized” state. Theuninitialized state indicated that the virtual disk extent is nodescribed by virtual disk file 702 and file system 414 is securingaccess to the virtual disk extent. That is, file system 414 isconfigured to prevent user applications from reading sectors within thisvirtual disk extent. In this example, the uninitialized state can beused to describe a virtual disk extent that was subject to a free spaceTRIM command. In the instance that the virtual disk extent is in theuninitialized state and an IO job indicative of a read to the extent isreceived, virtual disk parser 404 can respond with any data, i.e., a bitpattern from almost anywhere else in virtual disk file 702, zeros, ones,a non-information-disclosing bit pattern, etc., because virtual diskparser 404 is not providing security for the virtual disk extent, beyondthe requirement that only virtual disk payload data andnon-security-impacting metadata may be exposed to the virtual diskclient. In the instance that a write is directed to a virtual diskextent in this state, virtual disk parser 404 can simply allocate asection of the virtual disk file 702 without having to alter any datathat may be stored within the section. Consequently, this state is themost advantageous because space can be allocated within the virtual diskfile without clearing it beforehand. Virtual disk extent 5 of FIG. 7 isindicated as in the uninitialized state and virtual disk file 702 is notbacking the virtual disk extent.

Once state information is associated with each virtual disk extent,virtual disk parser 404 can be configured to provide additionalinformation to an administrator or the like about how virtual disk 402is arranged. In an example embodiment, virtual disk parser 404 can beconfigured to respond to offset queries that include certain parametersbased on the state information. For example, a user can issue a query toiterate, starting at a given byte offset, through virtual disk 402 andlocate ranges that satisfy a specific criteria such as “mapped,”“unmapped,” “transparent,” etc. In addition, a user can select how“deep” the query should go to take into account differencing virtualdisk files. For example, and referring to FIG. 7, a user could set adepth of 2 and execute a query. In response, virtual disk parser 404will execute the query on the last two virtual disk files in a chain,e.g., virtual disk files 610 and 612. Specific queries can include aquery to obtain the next non-transparent range(s), the next non-zerorange(s), the next defined range(s), the next initialized range(s), etc.Briefly, a query for the next defined range can be configured to returnthe next range(s) which contain defined data (e.g., sectors in themapped or zeroed state, with transparent sectors resolving to the parentvirtual disk file's state for that sector). A query for the nextinitialized range(s) can return the next range(s) which contain data ina state other than the uninitialized state, with transparent sectorsresolving to the parent virtual disk file's state for that sector.

Turning now to FIG. 8, it illustrates a specific example of how virtualdisk parser 404 can transition virtual disk extents from one state toanother in response to a file or other data being saved to virtual disk402. For example, suppose that a user uses a database management programwithin virtual machine 410 and creates a database. The user can save thedatabase in a file and file system 414 can determine where on virtualdisk 402 to save file 802. File system 414 can issue one or more diskwrites to write file 802 to, for example, sectors that fall withinvirtual disk extents 3-5. In this example, virtual disk extent 3 is“mapped” and virtual disk parser 404 can write the first portion of file802 to the section identified by allocation table 416.

Virtual disk extents 4 and 5, on the other hand, are in the “zero” and“uninitialized” state. In this example, virtual disk parser 404 canselect an unused section of virtual disk file 702 to back virtual diskextent 4 and determine that virtual disk extent 4 is in the zeroedstate. In response to this determination, virtual disk parser 404 canzero the section that is going to be used to describe virtual diskextent 4 or locate a section which is already all zeros. After locatinga zeroed section or the process of zeroing the section is complete,virtual disk parser 404 can generate information that identifies thevirtual disk file byte offset indicative of the fast byte of the sectionthat defines where virtual disk extent 4 is described in virtual diskfile 702 and store it in allocation table 416. Virtual disk parser 404can then change the state information associated with virtual diskextent 4 to indicate that it is “mapped.” Then the portion of the writeto extent 4 can be written to the located section.

Alternatively, for a portion of a write which covers an entire extent ofthe virtual disk currently in the zero state, a located section of thevirtual disk file may be chosen, the portion of the write may be issuedto the section, and upon completion of the write the virtual disk parser404 can then change the state information associated with the virtualdisk extent to indicate that the extent is “mapped”. Alternatively, fora portion of a write which only covers part of a virtual disk extentcurrently in the zero state, a located section of the virtual disk filemay be chosen, the portion of the write may be issued to the section, azeroing write may be issued to the remainder of the section, and oncompletion of the write the virtual disk parser 404 can then change thestate information associated with the virtual disk extent to indicatethat the extent is “mapped”. Those skilled in the art will recognizethat the given ordering of writes may be enforced using flush orwrite-through writes, such as force-unit-access writes.

Similarly, virtual disk parser 404 can select an unused section ofvirtual disk file 702 to back virtual disk extent 5 and determine thatvirtual disk extent 5 is in the uninitialized state by consultingallocation table 416. In response to this determination, virtual diskparser 404 can allocate the section to describe virtual disk extent 5without modifying the contents of the selected section. Virtual diskparser 404 can generate information that identifies the virtual diskfile byte offset indicative of the first byte of the section, whichindicates where virtual disk extent 4 is described in virtual disk file702 and store the file byte offset of the section in allocation table416. Virtual disk parser 404 can then change the state informationassociated with virtual disk extent 5 to indicate that it is “mapped.”

FIG. 9 illustrates another specific example of how virtual disk parser404 can transition virtual disk extents from one state to another inresponse to a deletion operation on file 802 and an operation that zerosthe contents of virtual disk extent 7. For example, a user may havedeleted file 802 and file system 414 may have issued a TRIM command. Inthis example, virtual disk parser 404 may receive a TRIM command thatincludes a range of virtual disk sectors that fully cover virtual diskextents 4 and 5 and partially cover virtual disk extent 3. In responseto a determination that virtual disk extent 4 and 5 are fully trimmed,virtual disk parser 404 can be configured to remove the linking fromallocation table 416 and transition virtual disk extent 4 to a statethat indicates that virtual disk file 702 is not backing this virtualdisk extent. As shown by the allocation table entry for virtual diskextent 4, the state virtual disk parser 404 transitions the virtual diskextent to depends on what states virtual disk parser 404 is configuredto use and whether or not file system 414 issues a free space TRIMcommand or a standard TRIM command. For example, virtual disk parser 404may be configured to use two states: mapped and zero to describe virtualdisk extents. Alternately, virtual disk parser 404 may be configured touse three states: mapped, zero, unmapped to describe virtual diskextents. Alternately, virtual disk parser 404 may be configured to usefour states: mapped, zero, unmapped, and uninitialized. The distinctionbetween unmapped and uninitialized corresponds to the distinctionbetween standard TRIM and free space TRIM. If the parser is configuredto not use the uninitialized state, then a free space TRIM is treated asa normal TRIM. As shown by the figure, the parts of file 702 are stillbeing stored in virtual disk file 702 since it is inefficient to clearthem from virtual disk file 702.

Since virtual disk extent 5 was partially covered by the TRIM, virtualdisk parser 404 can handle this extent in one of a variety of ways. Inone configuration, virtual disk parser 404 may leave extent 5 in themapped state. In this configuration, virtual disk parser 404 maytransition extents when TRIM information is received for an entireextent. Alternatively, virtual disk parser 404 may track TRIMinformation that partially covers extents in the hope that more TRIMinformation is received that provides an indication that spacedescribing the extent can be de-allocated.

Similarly, virtual disk extent was also partially covered by the TRIM.In this example, virtual disk parser 404 may leave it in the mappedstate and can also be configured to send TRIM information that describesthe part of virtual disk file 702 that is no longer in use to theunderlying file system, e.g., virtualization file system 408, storageserver file system 504, or computer system file system 514.

In addition to the deletion of file 802, FIG. 9 shows an example wherevirtual disk extent 7 was zeroed. Virtual disk parser 404 can scan an IOjob issued by file system 414 that indicates that the entire range ofvirtual disk extent 7 is zeroed. In response to this determination,virtual disk parser 404 can be configured to remove the linking fromextent allocation table 416 and transition virtual disk extent 7 to thezero state. As shown by the figure, the previous contents of virtualdisk extent 7 are still being stored in virtual disk file 702.

Turning to FIG. 10, it illustrates virtual disk 402 described at leastin part by a group of virtual disk files 1002, 1004, 1006, which couldbe similar to the chain of virtual disk files defined by virtual diskfile 608, 604, and 600. In this exemplary embodiment, the data thatrepresents virtual disk 402 is broken up across multiple virtual diskfiles. In this exemplary embodiment, when virtual disk parser 404attempts to read virtual disk extent 1 and 2, virtual disk parser 404can access the allocation table for virtual disk file 1002 and determinethat these extents are transparent. Next, virtual disk parser 404 canaccess the allocation table for virtual disk file 1004 and determinethat these extents are transparent. Finally, virtual disk parser 404 canaccess allocation table for grandparent virtual disk file 1006 anddetermine that these virtual disk extents are defined.

The following are a series of flowcharts depicting operationalprocedures. For ease of understanding, the flowcharts are organized suchthat the initial flowcharts present implementations via an overall “bigpicture” viewpoint and subsequent flowcharts provide further additionsand/or details that are illustrated in dashed lines. Furthermore, one ofskill in the art can appreciate that the operational procedure depictedby dashed lines are considered optional.

Referring now to FIG. 11, it illustrates an operational procedure forreclaiming space within a virtual disk file including the operations1100, 1102, 1104, and 1106. Operation 1100 begins the operationalprocedure and operation 1102 shows instantiating a virtual diskincluding a virtual disk extent, the virtual disk extent beingdissociated from a virtual disk file. Turning briefly to FIG. 4, FIG. 5Aor FIG. 5B, virtual disk 402 can be instantiated by virtual disk parser404, e.g., executable instructions and associated instance data, thatexposes the data stored within one or more virtual disk files as alogical hard drive, which can be configured to handle read/writeoperations from file system 414 by emulating the behavior of a harddrive. Virtual disk file 406 (which could be one or more files asillustrated in FIG. 6) can store what is typically found on a physicalhard drive, i.e., disk partitions, file systems, etc. Turning to FIG. 7,virtual disk 402 is shown including a plurality of extents, some ofwhich are dissociated from any sections of virtual disk file 702.

In a specific example, suppose the extents are blocks. In this example,allocation table 416, which can be loaded from one or more sections inthe virtual disk file 702 into random access memory, can be used tostore information that links virtual disk blocks in virtual disk 402 toextent sized (e.g., block sized) sections of virtual disk file 702.Allocation table 416 can also store state information for each virtualdisk block in virtual disk 402. Virtual blocks that potentially includenon-zero data can be associated with state information that indicatesthat the block is in the mapped state. That is, a section of virtualdisk file 702 has been allocated to describe, i.e., store data for, ablock of virtual disk 402. Virtual disk blocks 0-3 and 7 are examples ofblocks in this state. As shown by the figure, virtual disk blocks 4 and5, 6, 8 and 9 may be valid virtual disk blocks; however, these virtualdisk blocks may not have any space allocated within virtual disk file702. Since file system 414 may write to these blocks, in an exemplaryembodiment, these virtual disk blocks can be associated with informationthat can be used by virtual disk parser 404 to determine how to respondto read and/or write operations to them.

Referring briefly back to FIG. 11, operation 1104 shows that a computersystem can additionally include circuitry for allocating, based on stateinformation associated with the virtual disk, a section of the virtualdisk file to describe the virtual disk extent without overwriting apreexisting bit pattern within the section of the virtual disk file. Forexample, and returning to FIG. 8, virtual disk parser 404 can receive anIO job to write to a portion of the virtual disk extent. In response toreceipt of the write IO job, virtual disk parser 404 can checkallocation table 416 and determine that space within virtual disk file702 has not been allocated to describe the virtual disk extent andallocate a section of virtual disk file 406 to back the virtual diskextent. Thus, the data written by file system 414 to the virtual diskextent will be stored by virtual disk parser 404 in a section of virtualdisk file 702.

In this example, virtual disk parser 404 may not overwrite any dataalready stored in the section of virtual disk file 702 (by writing allzeros, ones, or any other non-information disclosing bit pattern) priorto using it to describe the virtual disk extent based on the stateinformation in allocation table 416. In an exemplary configuration, thestate information could indicate that file system 414 is securing accessto this virtual disk extent because the virtual disk extent is coveredby file system free space. In a specific example, the state informationcould indicate that the virtual disk extent is in the “uninitialized”state. Allocating the virtual disk extent without clearing it providesan added benefit of saving processor cycles and IO jobs that would beotherwise used to overwrite the section of virtual disk file 702.

In a specific example of operation 1104, and turning to FIG. 7, supposethat an extent is a block and file system 414 sends an IO job to virtualdisk 402 to write a bit pattern indicative of file 802 to virtual diskblocks 3-5. In response to receipt of such an IO job, virtual diskparser 404 can determine that virtual disk block 5 is not backed by anysections of virtual disk file 406 and that it is uninitialized. Inresponse to this determination, virtual disk parser 404 can beconfigured to allocate a section of virtual disk file 702 to describevirtual disk block 5 and write a portion of the bit pattern indicativeof file 802 therein without overwriting data that was previously storedin the portion of the section not covered by the IO job.

Turning again to FIG. 11, operation 1106 shows that the computer systemcan additionally include circuitry configured to modify the stateinformation associated with the virtual disk extent to indicate that thevirtual disk extent is described by the virtual disk file. For example,and turning back to FIG. 8, virtual disk parser 404 can modify, e.g.,overwrite in memory, the state information associated with virtual diskextent 5 to reflect that virtual disk file 702 is describing the virtualdisk extent. In one configuration, the write and the modification of thestate information can occur concurrently. For example, virtual diskparser 404 can store information in allocation table 416 that indicatesthat virtual disk extent 5 is “mapped.” Consequently, subsequent readoperations directed to sectors of virtual disk extent 5 will be handledby virtual disk parser 404 by returning the bit pattern stored at thebyte offset identified in allocation table 416. Virtual disk parser 404can concurrently write data, e.g., a bit pattern associated with a writeoperation that triggered this procedure, to the section of virtual diskfile 702 allocated to describe the virtual disk extent and issue an IOjob to a write the bit pattern to the section of virtual disk 702 tovirtualization system file system 408, storage server file system 504,or computer system file system 514. At some point in time, such as priorto completion of a subsequently issued flush command, the bit patternwill be persisted in persistent storage unit 460.

Turning now to FIG. 12, it shows additional operations that can beexecuted in conjunction with those illustrated by FIG. 11. Turning tooperation 1208, it indicates that the computer system can includecircuitry for responding to an offset query command with informationthat identifies sectors of the virtual disk that are non-zero, sectorsof the virtual disk that are in a non-transparent state, sectors of thevirtual disk that are in a mapped state, and/or sectors of the virtualdisk that are in an initialized state. For example, virtual disk parser404 can be configured to receive a command to generate information aboutvirtual disk 402 such as the next byte offset on the virtual disk, givena starting byte offset, that is in a non-transparent state, i.e., astate other than transparent, a mapped state, i.e., sectors of thevirtual disk 402 that include data in virtual disk file 406, a definedstate, i.e., sectors of the virtual disk 402 that arc mapped or zero,and/or an initialized state, i.e., a state other than uninitialized. Thecommand can be depth-limited, in that only a specified number of virtualdisk files are examined, with any ranges remaining transparent after thespecified number of virtual disk files are examined reported back to therequestor in addition to ranges indicated by the state query, regardlessof which state query was requested. In response to receipt of such acommand, virtual disk parser 404 can start at the initial byte offset onvirtual disk 402 and build a response range or set of ranges until therange associated with the command is detected and return the desiredinformation.

Continuing with the description of FIG. 12, operation 1210 shows sendinga request to a file system controlling the virtual disk file to issue atleast one command selected from a group of commands including a trimcommand, an unmap command, a write same of zero command, and an offloadwrite of a zero token command. Referring back to FIG. 4, FIG. 5A, orFIG. 5B, virtual disk parser 404 can be configured to issue a request tofile system 414. The request in this example can be for file system 414to issue a TRIM command. For example, virtual disk parser 404 can issueone or more requests to file system 414 periodically, soon afterinstantiation of virtual disk 402, and/or prior to shutting down,hibernating, etc., virtual machine 410. In response to such a request,file system 414 can determine what sectors of virtual disk 402 it is nolonger using and send one or more TRIM commands identifying these unusedsectors to virtual disk parser 404. Virtual disk parser 404 may therebyreceive trim information such as a list of ranges of sectors that are nolonger in use by file system 414 and whether file system 414 ispreventing reads from the ranges of sectors in order to secure access tothose sectors. Virtual disk parser 404 can receive the information andtransition virtual disk extents covered by the ranges into states wherespace within virtual disk file 702 can be reclaimed.

Continuing with the description of FIG. 12, operation 1212 shows thatthe computer system can include circuitry for determining a portion ofthe virtual disk file that corresponds to a portion of a second virtualdisk extent in response to receipt of a request to trim a portion of thesecond virtual disk extent; and circuitry for sending a trim command forthe determined portion of the virtual disk file to a file systemconfigured to store the virtual disk file on a storage device. Forexample, and referring to FIG. 8, file system 414 may issue a TRIMcommand that identifies a portion of a virtual disk extent, e.g., theTRIM command may only identify a range of sectors that corresponds to apart of the sectors that form one or more virtual disk blocks. In aspecific example, suppose file system 414 trims the space used to storefile 802. As such, the trim command may only identify a portion of thesectors that constitute virtual disk extent 3. In this example, virtualdisk parser 404 can determine that the range of sectors covers asubsection of the virtual disk extent and use mapping information inallocation table 416 to determine the portion of virtual disk file 702that corresponds to the trimmed sectors of the virtual disk extent.Virtual disk parser 404 can issue a request to trim the portion ofvirtual disk file 702 that corresponds to the trimmed sectors of thevirtual disk extent to virtualization system file system 408 or storageserver file system 504. Virtualization system file system 408 or storageserver file system 504 may be configured to use the trim command andbenefit from it by trimming a portion of the sectors backing virtualdisk file 406, flushing data from a cache, clearing internal buffers,etc.

Alternatively, virtual disk parser 404 can store information indicatingthat a portion of the virtual disk extent was trimmed as well asinformation that indicates whether it was a free space trim or not. Asguest operating system 412 or operating system 508 runs, it mayeventually zero or trim the remainder of the virtual disk extent. Inresponse to this occurring, virtual disk parser 404 can determine totransition the virtual disk extent into a state where it is notdescribed by virtual disk file 702 and select a state based on how thedifferent portions of the virtual disk extent were trimmed or zeroed.Virtual disk parser 404 can be configured to select the most restrictivestate to transition a virtual disk extent when different portions of avirtual disk extent can be placed in different non-described states,where the zero state is the most restrictive, uninitialized is the leastrestrictive state, and unmapped is somewhere in between. For example, ifa fast portion is zeroed and the remainder is uninitialized, virtualdisk parser 404 can transition the entire virtual disk extent to thezeroed state.

Continuing with the description of FIG. 12, operation 1214 illustratesthat computer system 400 can additionally include circuitry configuredto de-allocate the virtual disk extent from the section of the virtualdisk file and modify the state information associated with the virtualdisk extent to indicate that the virtual disk extent has no associatedspace in the virtual disk file in response to receipt of a request totrim a range of sectors that covers the virtual disk extent. Forexample, and turning to FIG. 9, virtual disk parser 404 can remove thelinking in allocation table 416 that ties a virtual disk extent to asection of virtual disk file 702. This operation has the effect ofdissociating the virtual disk extent from virtual disk file 702. Inaddition to removing the link, virtual disk parser 404 can modify thestate information associated with the virtual disk extent to indicatethat the extent has no associated space within virtual disk file 702,i.e., virtual disk parser 404 can place the virtual disk extent into theunmapped, uninitialized, or zeroed state.

Virtual disk parser 404 can remove the linking and update the stateinformation in response to receipt of a request to trim or zero sectorsof the virtual disk extent. For example, a request to trim or zerosectors can be received that identifies a range of byte offsets thatcould cover one or more virtual disk extents. In response to receipt ofsuch an IO job, virtual disk parser 404 can determine that the requestcovers the sectors of the virtual disk extent and execute theaforementioned operations for removing the linking and updating thestate information.

In a specific example, suppose that the IO job indicates that the trimis a free space trim. For example, a user may have deleted file 802,which is stored as a bit pattern across virtual disk extents 3-5 andfile system 414 may indicate that the space is no longer being used byfile system 414. In response to receipt of a free space TRIM command,virtual disk parser 404 can access allocation table 416 and determinethat file system 414 has trimmed a portion of extent 3, 5 and all ofextent 4. In this example, virtual disk parser 404 can remove the linkmapping virtual disk extent 4 to virtual disk file 702 and modify thestate information associated with virtual disk extent 4 to indicate thatthe virtual disk extent is uninitialized. This section of virtual diskfile 702 can now be reused to back other virtual disk extents. Inaddition, virtual disk parser 404 can determine that virtual disk extent3 and 5 are the subject of a partial TRIM command. In this example,virtual disk parser 404 can use allocation table 416 to discover thevirtual disk file byte offsets that describe the portion of virtual diskfile 702 that describes the trimmed portions of virtual disk extent 3and 5 and issue a TRIM command describing the virtual disk file byteoffsets to virtualization system file system 408, storage system filesystem 504, or computer system file system 514.

In another specific example, suppose that the IO job issued by filesystem 414 indicates that file 802 was zeroed. For example, file 802could be a database file storing sensitive information such as creditcard numbers and an administrator determined to zero out the contents ofthe file by writing all zeros to it by issuing a write command with anall-zero buffer, which will write zeros over the data existing in file802. In response to receipt of such an IO job, virtual disk parser 404can be configured to determine that virtual disk extent 4 has beenzeroed and that this extent can be reclaimed. In this example, virtualdisk parser 404 can remove the link mapping virtual disk extent 4 tovirtual disk file 702 and modify the state information associated withvirtual disk extent 4 to indicate that the virtual disk extent iszeroed. This section of virtual disk file 702 can now be reused to backother virtual disk extents and virtual disk parser 404 can respond tosubsequent read operations to virtual disk extent 4 by replying with allzeros.

In another specific example, a user may write bulk zeros to initializethe state of file 802, rather than to overwrite data stored therein. Inthis example, a command such as a TRIM, in the instance that virtualdisk parser 404 reports that trimmed sections read as zero, UNMAP, whenvirtual disk parser 404 reports that unmapped regions are zero, WRITESAME of zero, and/or an offload write of a zero token can be used totransition an extent to the zeroed state.

In a specific example, suppose that the IO job indicates that the trimis a standard trim. For example, a user may have deleted file 802, whichis stored as a bit pattern across virtual disk extents 3-5; however, theTRIM command may not indicate whether or not the space is being used byfile system 414. In response to receipt of a standard TRTM command,virtual disk parser 404 can access allocation table 416 and determinethat file system 414 has trimmed a portion of extent 3, 5 and all ofextent 4. In this example, virtual disk parser 404 can remove the linkmapping virtual disk extent 4 to virtual disk file 702 and modify thestate information associated with virtual disk extent 4 to indicate thatthe virtual disk extent is unmapped or zero. This section of virtualdisk file 702 can now be reused to describe other virtual disk extents.In addition, virtual disk parser 404 can determine that virtual diskextent 3 and 5 are the subject of a partial TRIM command. In thisexample, virtual disk parser 404 can use allocation table 416 todiscover the virtual disk file byte offsets that make up the portion ofvirtual disk file 702 that describes the trimmed portions of virtualdisk extent 3 and 5 and issue a TRIM command specifying the virtual diskfile byte offsets, typically in the form of ranges, to virtualizationsystem file system 408.

Referring now to FIG. 13, which illustrates additional operations thatcan be executed in addition to operation 1214 of FIG. 12. Operation 1316illustrates that a computer system can include circuitry for receiving arequest to write data to the virtual disk extent; circuitry for zeroingan unused section of the virtual disk file based on the stateinformation associated with the virtual disk extent, the stateinformation indicating that the virtual disk extent was zeroed; andcircuitry for allocating the unused section of the virtual disk file todescribe the virtual disk extent. Referring to FIG. 9 for context,virtual disk parser 404 can receive a request to write data to thevirtual disk extent, e.g., virtual disk extent 4 of FIG. 9, which inthis example is associated with state information that indicates thatthe virtual disk extent is zeroed. For example, when virtual disk extent4 was de-allocated virtual disk parser 404 could have determined thatthe virtual disk extent was zeroed, i.e., an application wrote all zerosto file 602 by using an offload write of a well-known zero token.

In response to determining that the virtual disk extent is in the zeroedstate, virtual disk parser 404 can identify an unused section of virtualdisk file 702, i.e., a section that is not actively being used todescribe a virtual disk extent and not actively being used to store anyallocated metadata, and use the section to back the virtual disk extent.The virtual disk parser further insures that any reads fromnot-yet-written sectors of the newly allocated extent read as all zeros.The virtual disk parser 404 can write payloads of IO write jobs to thesection; update state information to indicate that the virtual diskextent is mapped; and update information in allocation table 416 todescribe the virtual disk file byte offset that identifies the beginningof the section used to store virtual disk extent 4. The virtual diskparser 404 also can create a log entry, which insures that in the eventof system failure and re-start prior to writes being flushed,not-yet-written sectors of the newly allocated extent still read as allzeros, and written sectors of the newly allocated extent read as eitherall zeros or the written data. Upon the first subsequent flush command,virtual disk parser 404 insures that a system failure subsequent tocompletion of the flush will result in reads from previously writtensectors of the newly allocated extent reading the data that was written,and reads from not-yet-written sectors of the newly allocated extentreading zeros.

Continuing with the description of FIG. 13, operation 1318 shows that acomputer system can include circuitry for receiving a request to writeto the virtual disk extent; and circuitry for allocating an unusedsection of the virtual disk file to describe the virtual disk extentwithout modifying contents of the unused section of the virtual diskfile based on the state information associated with the virtual diskextent, the state information indicating that the file system issecuring access to the virtual disk extent. Referring again to FIG. 9for context, virtual disk parser 404 can receive an IO job lo write datato the virtual disk extent, e.g., virtual disk extent 4 of FIG. 9, whichin this example is associated with state information that indicates thatsecurity for the virtual disk extent is being provided by file system414. In response to detecting this state information, virtual diskparser 404 can identify an unused section of virtual disk file 702;write the payload of the IO job to the section; update state informationto indicate that the virtual disk extent is mapped; and updateinformation in allocation table 416 to describe the virtual disk filebyte offset that identifies the beginning of the section used to storevirtual disk extent 4.

Suppose that in this example the extent is a block and the payload forthe IO job only covers a portion of the sectors in the virtual diskblock. Specifically, the virtual disk block may be 512 kilobytes and thewrite may cover the first 500 sectors of the virtual disk block. In thisexample, virtual disk parser 404 can write data in the first 500 sectorsof the allocated section of virtual disk file 702 without erasing thedata stored in the remaining 524 sectors. Thus, if this section wasexamined one would find that the first 500 sectors include the payloadand the remaining 524 sectors include whatever bit pattern waspreviously written to the section of virtual disk file 702. In thisexample, virtual disk parser 404 can use this section without clearingit because file system 414 is configured to deny read operations tosectors that are in file system free space. Since an application will beprevented from reading the remaining 524 sectors of virtual disk block,it can contain any data, which had previously been stored in the virtualdisk.

Turning now to operation 1320 of FIG. 13, it shows that a computersystem can be configured to include circuitry for receiving a request towrite to the virtual disk extent; circuitry for logically overwriting anunused section of the virtual disk file with anon-information-disclosing bit pattern based on the state informationassociated with the virtual disk extent, the state informationindicating that the file system is not securing access to the virtualdisk extent; and circuitry for allocating the overwritten section of thevirtual disk file to describe the virtual disk extent. Referring againto FIG. 9 for context, virtual disk parser 404 can receive a request towrite data to the virtual disk extent, which in this example isassociated with state information that indicates that file system 414 isnot securing access to the virtual disk extent. For example, virtualdisk parser 404 may have de-allocated the virtual disk extent inresponse to receipt of a standard TRIM command and could have storedstate information indicating that virtual disk extent is unmapped, i.e.,not backed by space in virtual disk file 702, in allocation table 416.

In response to determining that the virtual disk extent is unmapped,virtual disk parser 404 can identify an unused section of virtual diskfile 702 to use to describe the virtual extent and logically write anon-information disclosing bit pattern to the section to ensure thatreads to the virtual disk extent do not inadvertently reveal anyinformation. In a preferred implementation, thenon-information-disclosing bit pattern could be all zeros orpreviously-stored data. After the section is zeroed or some othernon-information disclosing bit pattern is logically written to thesection such as previously-stored data, virtual disk parser 404 canlogically write the payload of an IO job to the section; update stateinformation to indicate that the virtual disk extent is mapped; andupdate information in allocation table 416 to describe the virtual diskfile byte offset that identifies the beginning of the section used tostore the virtual disk extent.

Continuing with the description of FIG. 13, operation 1322 shows thatthe computer system can include circuitry configured to send, based onstate information indicating that the virtual disk extent was zeroed, atoken representing zeros to a requestor in response to receipt of anoffload read request associated with the virtual disk extent. Forexample, and referring to FIG. 4, offload provider engine 422, e.g.,circuitry configured to service offload read and offload write commands,can send a token representing zeros to a requestor, e.g., application424, in a response to an offload read request issued by the requestor.An offload read request can be used to efficiently copy data from onelocation to another by generating and sending tokens to requestors, thetokens representing the requested data instead of copying the data intothe requestors' memory and then sending the data to the destination.Offload read and offload write commands can be used to achieve copyoffload when the destination location recognizes the token generated bythe source location and can logically write the data represented by thetoken to the destination. In the case of a well-known zero tokengenerated by the source, the destination need not access the underlyingstorage, e.g., storage device 106, which could be a SAN target in thisspecific implementation. In this example, the offload read request canbe to perform an offload read operation on one or more files that havedata stored in one or more virtual disk extents, one of which isassociated with state information indicating that the virtual diskextent is zeroed. In this example, the offload read request may beserviced by generating a well-known zero token value and returning thatwell-known zero token to the requestor.

The offload read request can be routed to offload provider engine 422.Offload provider engine 422 can receive the request and send a messageto virtual disk parser 404 for the data stored in the virtual diskextents. Virtual disk parser 404 can receive the request, read the stateinformation for the virtual disk extent, and determine, in this specificexample, that the state information indicates that this virtual diskextent is zeroed. Virtual disk parser 404 can send a message back tooffload provider engine 422 that indicates that the virtual disk extentis all zeros and offload provider engine 422 can generate a well-knowntoken value that indicates that the requested data is all zeros, e.g.,the range of sectors that describes a virtual disk block is all zeros,and send the well-known zero token to the requestor.

In a specific example, the offload request can be forward to a SANinstead of being processed by computer system 400, storage service 500,or computers system 512. In this example, the SAN may generate the tokenand return it back to virtual disk parser 404, which can then send thezero token to the requestor. In yet another example, when offloadprovider engine 422 receives the message that indicates that the virtualdisk extent is all zeros, offload provider engine 422 can generate thewell-known zero token, which in effect achieves logically copying therequested zero data into a separate area that is associated with thetoken by identifying the data as equivalent to any other zero data andsharing the area associated with the well-known zero token. In theinstance that offload provider engine 422 subsequently receives anoffload write specifying the token previously sent to the requestor,offload provider engine 422 can logically copy the data from the areaassociated with the token to offsets specified by the requestor.

Turning now to FIG. 14, it illustrates an operational procedure forreclaiming virtual disk file space including the operations 1400, 1402,1404, and 1406. As shown by the figure, operation 1400 begins theoperational procedure and operation 1402 shows that a computer systemcan include circuitry for receiving a signal indicating that a portionof a virtual disk extent is no longer in use, the virtual disk extentbeing part of a virtual disk, the virtual disk being stored in a virtualdisk file. For example, and turning to FIG. 4, virtual disk parser 404can be configured to instantiate virtual disk 402. File system 414 cansend a signal indicating that it is no longer using a portion of virtualdisk 402, e.g., a range of sectors of a virtual disk extent, to virtualdisk parser 404. In a specific example, the signal could be a TRIMcommand. In a specific example, the signal received by virtual diskparser 404 could identify byte offset values that define a range ofsectors that it is no longer using, which could be the first part of avirtual disk extent.

Continuing with the description of FIG. 14, operation 1404 shows thatthe computer system can also include circuitry configured to identify aportion of the virtual disk file that describes the portion of thevirtual disk extent. Referring back to FIG. 7, virtual disk parser 404can receive the signal and the virtual disk byte offset values thatidentify, for example, the first portion of virtual disk extent 0. Inresponse to receipt of the signal, virtual disk parser 404 can checkallocation Table 416 to determine the portion of virtual disk file 702that corresponds to the virtual disk byte offset values associated withthe signal.

Turning now to operation 1406 of FIG. 14, it shows that the computersystem can include circuitry for sending a request to trim theidentified portion of the virtual disk file to a file system configuredto store the virtual disk file on a storage device. For example, andagain referring to FIG. 7, virtual disk parser 404 can determine thatthe signal identified less than the entire virtual disk extent. Forexample, the signal may indicate a range of sectors that does notinclude all of the sectors of a virtual disk extent. In response to thisdetermination, virtual disk parser 404 can issue a request to trim theportion of virtual disk file 702 that corresponds to the trimmed portionof the virtual disk extent to a file system hosting virtual disk file702, e.g., virtualization system file system 408. Virtualization systemfile system 408 may be configured to use the trim command and benefitfrom it by trimming virtual disk file 406, flushing data from a cache,clearing internal buffers, sending the trim to the disk on which thefile system data is stored, etc.

In a specific example, virtual disk parser 404 can be configured toissue the TRIM command to the underlying file system in response todetermining that the request to trim a portion of the virtual disk filedoes not cover the entire extent. For example, suppose that the signalidentifies that the first 600 sectors of a virtual disk extent are nolonger in use and virtual disk parser 404 may determine that the 600sectors of virtual disk extent are less than the 1024 sectors thatconstitute the virtual disk extent. In response to this determination,virtual disk parser 404 can access allocation table 416 and determinethe virtual disk file byte offsets that describe the first 600 sectorsof the section of virtual disk file 702 that describes the virtual diskextent and send a request to trim this part of virtual disk file 702 toa file system that hosts virtual disk file 702.

Turning now to FIG. 15, it illustrates additional operations that can beexecuted in conjunction with those depicted by FIG. 14. Turning now tooperation 1508, it shows that the computer system can additionallyinclude circuitry for sending, based on state information indicatingthat the virtual disk extent was zeroed, a token representing zeros to arequestor in response to receipt of an offload read request associatedwith the virtual disk extent. For example, and referring to FIG. 4,offload provider engine 422, e.g., circuitry configured to serviceoffload read and offload write commands, can send a token representingzeros to a requestor, e.g., application 424, in a response to an offloadread request issued by the requestor. An offload read request can beused to efficiently copy data from one location to another by generatingand sending tokens to requestors, the tokens representing the requesteddata instead of copying the data into the requestors' memory and thensending the data to the destination. Offload read and offload writecommands can be used to achieve copy offload when the destinationlocation recognizes the token generated by the source location and canlogically write the data represented by the token to the destination. Inthe case of a well-known zero token generated by the source, thedestination need not access the underlying storage, e.g., storage device106, which could be a SAN target in this specific implementation. Inthis example, the offload read request can be to perform an offload readoperation on one or more files that have data stored in one or morevirtual disk extents, one of which is associated with state informationindicating that the virtual disk extent is zeroed. In this example, theoffload read request may be serviced by generating a well-known zerotoken value and returning that well-known zero token to the requestor.

Continuing with the description of FIG. 15, operation 1510 shows thatthe computer system can include circuitry for selecting a sub-group fromthe group of virtual disk files; and circuitry for generatinginformation that identifies sectors of the sub-group that include dataand sectors of the sub-group that are transparent. In an exemplaryembodiment, virtual disk 402 can be instantiated from a plurality ofvirtual disk files. Or put another way, virtual disk 402 can be formedfrom M virtual disk files (where M is an integer greater than 1). Inthis exemplary embodiment, virtual disk parser 404 can be configured toreceive a request from, for example, an administrator, to determine thenext byte offset on virtual disk 402, starting at a given byte offset,that is associated with a sector defined within a subgroup of thevirtual disk files. For example, and referring to FIG. 10, virtual diskparser 404 may receive a request for the next defined byte offsetstarting at the virtual disk offset corresponding to the first sector ofvirtual disk extent 2 and information indicating that the subgroupincludes virtual disk file 1002 and virtual disk file 1004. In thisexample, virtual disk parser 404 can start scanning through subgroup anddetermine that the next defined byte offset is the sector thatcorresponds to the beginning of virtual disk extent 3. Since in thisexample, the data in virtual disk extent 2 is backed by a section ofvirtual disk file 1006 it is outside of the search and is not returnedas being defined.

Continuing with the description of FIG. 15, operation 1512 shows thatthe computer system can include circuitry configured to dissociate thevirtual disk extent from the virtual disk file and modify stateinformation associated with the virtual disk extent to indicate that thevirtual disk extent has been zeroed in response to determining that thevirtual disk extent was zeroed. For example, and turning to FIG. 7, inan embodiment virtual disk parser 404 can determine that the virtualdisk extent has been zeroed. For example, virtual disk parser 404 canreceive a request to write data represented by a well-known zero tokento the virtual disk extent, e.g., virtual disk extent 7. Virtual diskparser 404 can determine from a data structure associated with therequest that the request is for the entire virtual disk extent, i.e.,the byte offset values can start al the first sector or extent 7 and endal the last sector or extent 7. In response to such a determination, andinstead of writing the zeros to the corresponding section of virtualdisk file 702, virtual disk parser 404 can be configured to remove thelink that maps virtual disk extent 7 to a section of virtual disk file702 used to describe virtual disk extent 7 and associate the virtualdisk extent with information that indicates that the virtual disk extentis all zeros. For example, virtual disk parser 404 can write eight bytesof information in allocation table 416 that indicates that the virtualdisk extent includes all zeros. The end result of this operation is thatthe section of virtual disk file 702 can be reused to store data forother virtual disk extents and the virtual disk extent will read as ifit includes all zeros, even though no portion of the virtual disk fileis describing the extent on a bit-for-bit basis.

Continuing with the description of FIG. 15, operation 1514 shows thatthe computer system can additionally include circuitry configured todissociate the virtual disk extent from the virtual disk file and modifystate information associated with the virtual disk extent to indicatethat the virtual disk extent is free space in response to adetermination that the virtual disk extent is considered free space by afile system. For example, and again turning to FIG. 7, virtual diskparser 404 can determine that file system 414 has associated the virtualdisk extent with information that indicates that it is free space, i.e.,space that is not used by file system 414. For example, virtual diskparser 404 can receive a signal from file system 414 indicating a rangeof sectors that covers the virtual disk extent, e.g., virtual diskextent 3, and information that indicates that the sectors are consideredto be free space. In response to receipt of such a signal, virtual diskparser 404 can be configured to remove information that links thevirtual disk extent to a section of virtual disk file 702. The result ofthis operation is that the section of virtual disk file 702 can bereused to store data for other virtual disk extents. Virtual disk parser404 can additionally associate the virtual disk extent with informationthat indicates that the virtual disk extent includes arbitrary data,i.e., data previously stored in any part of the virtual disk, all zeros,or all ones. Consequently, read operations directed to this virtual diskextent can be handled by returning arbitrary data which was previouslystored in the virtual disk. In addition, the arbitrary data canoptionally change each time a read operation is received, if the virtualdisk parser 404 is configured to allow the arbitrary data to change eachtime a read operation is received.

Continuing with the description of FIG. 15, operation 1516 shows thatthe computer system can additionally include circuitry configured todissociate the extent from the virtual disk file and modify slateinformation associated with the virtual disk extent to indicate that thevirtual disk extent includes a non-information-disclosing bit pattern inresponse to a determination that the virtual disk extent was trimmed.For example, and again turning to FIG. 7, virtual disk parser 404 candetermine that file system 414 has trimmed a range of sectors thatcompose a virtual disk extent. In response to such a determination,virtual disk parser 404 can remove information in allocation table 416that links the virtual disk extent to a section of virtual disk file702. The result of this operation is that the section of virtual diskfile 702 can be reused to store data for other virtual disk extents.Virtual disk parser 404 can additionally associate the virtual diskextent with information that indicates that the virtual disk extentincludes a non-information-disclosing bit pattern, e.g., all zeros,ones, or a randomly generated bit pattern. Consequently, read operationsdirected to this virtual disk extent can be handled by returning thenon-information-disclosing bit pattern. In a specific preferredimplementation, the non-information-disclosing bit pattern can be allzeros. However, this is different than the zero state described above inthat the zero state can be used to represent meaningful zeros, i.e., theinstance where the virtual disk extent was intentionally zeroed.

Referring to operation 1518, it shows that the computer system canadditionally include circuitry configured to send a request to issue atrim command to a file system controlling the virtual disk. Referringback to FIG. 7, virtual disk parser 404 can be configured to issue arequest that file system 414 issue one or more TRIM commands. In anexemplary configuration, virtual disk parser 404 can be configured toperiodically send such a request or to send such a request based onpredetermined criteria, e.g., when VM 410 starts or shortly before theVM is to be shut down. In response to such a request, file system 414can issue one or more TRIM commands that identify the unused sectors ofvirtual disk 402 to virtual disk parser 404. Virtual disk parser 404 maythen receive trim information from the TRIM commands such as the rangeof sectors that are no longer in use by file system 414 and optionallyinformation that indicates whether the trimmed sectors are consideredfree space. Virtual disk parser 404 can receive the information and useit to update state information stored in allocation table 416 and topossibly reclaim unused sections of virtual disk file 702.

Turning now to FIG. 16, it illustrates an operational procedure forstoring data for a virtual machine. The operational procedure beginswith operation 1600 and transitions to operation 1602, which describesan instance where a computer system can include circuitry for executinga guest operating system including a file system within a virtualmachine. For example, and referring to FIG. 4, virtualization system420, which could be hypervisor 302 of FIG. 3 or the combination offunctions executed by host environment 204 and microkernel hyper visor202 of FIG. 2, can instantiate virtual machine 410 and run a guestoperating system (such as guest operating system 412) within it. In thisexample, guest operating system 412 can include file system 414, whichcan be executable instructions that organize and control data for guestoperating system 412.

Continuing with the description of FIG. 16, operation 1604 shows thatthe computer system can include circuitry for exposing a virtual storagedevice to the guest operating system, the virtual storage deviceincluding a virtual disk extent, the virtual disk extent beingdissociated from a virtual disk file. Turning back to FIG. 4,virtualization system 420 can expose virtual disk 402 to guest operatingsystem 412. For example, virtual disk parser 404 can be in communicationwith a storage virtualization service provider that is operable tocommunicate with a storage virtualization service client running withinguest operating system 410. In a specific example, the storagevirtualization service client could be a driver installed within guestoperating system 412 that signals to the guest that it can communicatewith a storage device. In this example, IO jobs sent by file system 414are sent first to the storage virtualization service client and then tothe storage virtualization service provider via a communication channel,e.g., a region of memory and cross-partition notification facility.Virtual disk 402 can be composed from one or more virtual disk files 406that can be opened by virtual disk parser 404 and used to store data forvirtual disk 402. In a specific example virtual disk 402 can bedescribed at least in part by virtual disk file 702 of FIG. 7. Inanother specific example, and turning to FIG. 10, virtual disk 402 canbe described by a group of virtual disk files (1002-1006). In eithercase, and returning to FIG. 4, virtual disk 402 can include a pluralityof virtual disk extents and one of the virtual disk extents candissociated, i.e., not described on a bit-for-bit basis by any spacewithin its associated virtual disk file.

Continuing with the description of FIG. 16, operation 1606 shows thatthe computer system can include circuitry for receiving a request towrite data to the virtual disk extent. Turning back to FIG. 7, virtualdisk parser 404 can receive a request to write data to the virtual diskextent that has no associated space within virtual disk file 702. Forexample, an IO job can be received that specifies an offset valueindicative of the address of a virtual disk sector, which is within thevirtual disk extent.

Turning back to FIG. 16, operation 1608 shows that the computer systemcan optionally include circuitry for determining that state informationassociated with the virtual disk extent indicates that the virtual diskextent is free space. In response to receipt of the IO job, virtual diskparser 404 can access allocation table 416 and read state informationassociated with the virtual disk extent. In this example, the virtualdisk extent may be associated with information that indicates that thevirtual disk extent is free space, i.e., that file system 414 is notusing the virtual disk extent and that read operations to the virtualdisk extent can be answered with arbitrary data.

Referring to FIG. 16, operation 1610 shows that the computer system canoptionally include circuitry for allocating a section of the virtualdisk file to describe the virtual disk extent without overwriting apreexisting bit pattern within the section of the virtual disk file. Forexample, and returning to FIG. 7, in response to receipt of a write IOjob, virtual disk parser 404 can locate a section in virtual disk file702 that is not being used and allocate it to store data for the virtualextent. For example, virtual disk parser 404 can write information inallocation table 416 that links the virtual disk extent to byte offsetvalues of the allocated section of virtual disk file 702.

In this example, virtual disk parser 404 may not overwrite any bitpattern existing within the section, e.g., data from some deleted fileand/or arbitrary data, stored in the section of virtual disk file 702(by writing all zeros, ones, or any other non-information-disclosing bitpattern) prior to using the section to describe the virtual disk extentbecause state information indicates that file system 414 has identifiedvirtual disk extent 5 as free space. This provides an added benefit ofsaving processor cycles and IO jobs that would be otherwise used tooverwrite the section of the virtual disk extent.

Referring to operation 1612 of FIG. 16, it shows that the computersystem can optionally include circuitry for modifying the stateinformation associated with the virtual disk extent to indicate that thevirtual disk extent is mapped to the allocated section of the virtualdisk file. For example, and turning back to FIG. 7, virtual disk parser404 can modify, e.g., overwrite in memory, the state informationassociated with the virtual disk extent to indicate that it is mapped.Consequently, subsequent read operations directed to sectors of thevirtual disk extent will be handled by virtual disk parser 404 byreturning the bit pattern stored in corresponding portions of theallocated section.

Turning now to operation 1614 of FIG. 16, it shows storing the data tothe allocated section of the virtual disk file. Turning back to FIG. 6,virtual disk parser 404 can write the data, e.g., a bit pattern, intovirtual disk file 702. An IO job indicative of the write to virtual diskfile 702 can be issued to virtualization system file system 408 andeventually the change can be persisted by persistent storage unit 460.

Turning now to FIG. 17, it shows additional operations that can beexecuted in conjunction with those illustrated by FIG. 16. Turningattention to operation 1716, it shows that the computer system canoptionally include circuitry for dissociating the virtual disk extentfrom the virtual disk file and modifying the state informationassociated with the virtual disk extent to indicate that the virtualdisk extent has been zeroed in response to determining that the virtualdisk extent was zeroed. For example, and turning to FIG. 6, in anembodiment virtual disk parser 404 can determine that the virtual diskextent has been zeroed. For example, virtual disk parser 404 can receivean offload write request to write data represented by a well-known zerotoken to the virtual disk extent, e.g., virtual disk extent 7. Virtualdisk parser 404 can determine from a data structure associated with therequest that the request is for the entire virtual disk extent, i.e.,the byte offset values can start at the first sector of virtual diskextent 7 and end at the last sector of virtual disk extent 7. Inresponse to such a determination, and instead of writing the zeros tothe corresponding section of virtual disk file 702, virtual disk parser404 can be configured to remove the link from the virtual disk extent toa section of virtual disk file 702 stored in allocation table 416 andassociate the virtual disk extent with information that indicates thatthe virtual disk extent is all zeros.

Continuing with the description of FIG. 17, operation 1718 shows thatthe computer system can optionally include circuitry for dissociatingthe virtual disk extent from the virtual disk file and modifying thestate information associated with the virtual disk extent to indicatethat the virtual disk extent includes arbitrary data in response toreceipt of a signal from a file system identifying the virtual diskextent as free space. For example, and again turning to FIG. 7, virtualdisk parser 404 can determine that file system 414 has associated thevirtual disk extent with information that indicates that it is freespace, i.e., space that is not used by file system 414. For example,virtual disk parser 404 can receive a signal from file system 414indicating a range of sectors that covers the virtual disk extent, e.g.,virtual disk extent 3, and information that indicates that the sectorsare free space. In response to such a determination, virtual disk parser404 can be configured to remove information in allocation table 416 thatlinks the virtual disk extent to a section of virtual disk file 702 andassociate the virtual disk extent with information that indicates thatarbitrary data, i.e., data previously stored in any part of the virtualdisk, all zeros, or all ones, can be returned in response to receipt ofa read IO job.

Operation 1720 of FIG. 17 shows that computer system 400 can optionallyinclude circuitry for dissociating the virtual disk extent from thevirtual disk file and modifying the state information associated withthe virtual disk extent to indicate that the virtual disk extentincludes a non-information disclosing bit pattern in response to receiptof a request to trim all the sectors of the virtual disk extent. Forexample, and again turning to FIG. 7, virtual disk parser 404 candetermine that the sectors that compose a virtual disk extent have beentrimmed. For example, virtual disk parser 404 can receive a trim commandfrom file system 414 indicating a range of sectors that covers thevirtual disk extent. In response to receipt of such a signal, virtualdisk parser 404 can be configured to remove information in allocationtable 416 that links the virtual disk extent to a section of virtualdisk file 702 and associate the virtual disk extent with informationthat indicates that the virtual disk extent includes anon-information-disclosing bit pattern.

The foregoing detailed description has set forth various embodiments ofthe systems and/or processes via examples and/or operational diagrams.Insofar as such block diagrams, and/or examples contain one or morefunctions and/or operations, it will be understood by those skilled inthe art that each function and/or operation within such block diagrams,or examples can be implemented, individually and/or collectively, by awide range of hard ware, software, firmware, or virtually anycombination thereof.

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of the subject matter described herein.

What is claimed:
 1. A computer-readable storage medium includinginstructions that upon execution by a processor cause the processor to:instantiate a virtual disk including a virtual disk extent, the virtualdisk extent being dissociated from a virtual disk file; allocate, basedon state information associated with the virtual disk, a section of thevirtual disk file to describe the virtual disk extent withoutoverwriting a preexisting bit pattern within the section of the virtualdisk file; and modify the state information associated with the virtualdisk extent to indicate that the virtual disk extent is described by thevirtual disk file.
 2. The computer-readable storage medium of claim 1,further comprising instructions that upon execution cause the processorto: respond to an offset query command with information that identifiessectors of the virtual disk that are non-zero, sectors of the virtualdisk that are in a non-transparent state, sectors of the virtual diskthat are in a mapped state, and/or sectors of the virtual disk that arein an initialized state.
 3. The computer-readable storage medium ofclaim 1, further comprising instructions that upon execution cause theprocessor to: send a request to a file system controlling the virtualdisk file to issue at least one command selected from a group ofcommands including a trim command, an unmap command, a write same ofzero command, and an offload write of a zero token command.
 4. Thecomputer-readable storage medium of claim 1, further comprisinginstructions that upon execution cause the processor to: determine aportion of the virtual disk file that corresponds to a portion of asecond virtual disk extent in response to receipt of a request to trim aportion of the second virtual disk extent; and send a trim command forthe determined portion of the virtual disk file to a file systemconfigured to store the virtual disk file on a storage device.
 5. Thecomputer-readable storage medium of claim 1, further comprisinginstructions that upon execution cause the processor to: dissociate thevirtual disk extent from the section of the virtual disk file and modifythe state information associated with the virtual disk extent toindicate that the virtual disk extent has no associated space in thevirtual disk file in response to receipt of a request to trim a range ofsectors that covers the virtual disk extent.
 6. The computer-readablestorage medium of claim 5, further comprising instructions that uponexecution cause the processor to: receive a request to write data to thevirtual disk extent; zero an unused section of the virtual disk filebased on the state information associated with the virtual disk extent,the state information indicating that the virtual disk extent waszeroed; and allocate the unused section of the virtual disk file todescribe the virtual disk extent.
 7. The computer-readable storagemedium of claim 5, further comprising instructions that upon executioncause the processor to: receive a request to write to the virtual diskextent; and allocate an unused section of the virtual disk file todescribe the virtual disk extent without modifying contents of theunused section of the virtual disk file based on the state informationassociated with the virtual disk extent, the state informationindicating that the file system is securing access to the virtual diskextent.
 8. The computer-readable storage medium of claim 5, furthercomprising instructions that upon execution cause the processor to:receive a request to write to the virtual disk extent; overwrite anunused section of the virtual disk file with anon-information-disclosing bit pattern based on the state informationassociated with the virtual disk extent, the state informationindicating that the file system is not securing access to the virtualdisk extent; and allocate the overwritten section of the virtual diskfile to describe the virtual disk extent.
 9. The computer-readablestorage medium of claim 5, further comprising instructions that uponexecution cause the processor to: send, based on state informationindicating that the virtual disk extent was zeroed, a token representingzeros to a requestor in response to receipt of an offload read requestassociated with the virtual disk extent.
 10. A computer system,comprising: a processor; a memory coupled to the processor when theprocessor and the memory are powered, the memory including instructionsthat upon execution by the processor cause the computer system to:receive a signal indicating that a portion of a virtual disk extent isno longer in use, the virtual disk extent being part of a virtual disk,the virtual disk being stored in a virtual disk file; identify a portionof the virtual disk file that describes the portion of the virtual diskextent; and send a request to trim the identified portion of the virtualdisk file to a file system configured to store the virtual disk file ona storage device.
 11. The computer system of claim 10, the memoryfurther comprising instructions that upon execution cause the computersystem to: send, based on state information indicating that the virtualdisk extent was zeroed, a token representing zeros to a requestor inresponse to receipt of an offload read request associated with thevirtual disk extent.
 12. The computer system of claim 10, the virtualdisk file being a member of a group of virtual disk files that togetherform a virtual disk that includes the virtual disk extent and the memoryfurther comprising instructions that upon execution cause the computersystem to: select a sub-group from the group of virtual disk files; andgenerate information that identifies sectors of the sub-group thatinclude data and sectors of the sub-group that are transparent.
 13. Thecomputer system of claim 10, the memory further comprising instructionsthat upon execution cause the computer system to: dissociate the virtualdisk extent from the virtual disk file and modify state informationassociated with the virtual disk extent to indicate that the virtualdisk extent has been zeroed in response to determining that the virtualdisk extent was zeroed.
 14. The computer system of claim 10, the memoryfurther comprising instructions that upon execution cause the computersystem to: dissociate the virtual disk extent from the virtual disk fileand modify state information associated with the virtual disk extent toindicate that the virtual disk extent is free space in response to adetermination that the virtual disk extent is considered free space by afile system.
 15. The computer system of claim 10, the memory furthercomprising instructions that upon execution cause the computer systemto: dissociate the extent from the virtual disk file and modify stateinformation associated with the virtual disk extent to indicate that thevirtual disk extent includes a non-information-disclosing bit pattern inresponse to a determination that the virtual disk extent was trimmed.16. The computer system of claim 10, the memory further comprisinginstructions that upon execution cause the computer system to: send arequest to issue a trim command to a file system controlling the virtualdisk.
 17. A computer implemented method for storing data for a virtualmachine, comprising: executing a guest operating system including a filesystem within a virtual machine; exposing a virtual storage device tothe guest operating system, the virtual storage device including avirtual disk extent, the virtual disk extent being dissociated from avirtual disk file; receiving a request to write data to the virtual diskextent; determining that state information associated with the virtualdisk extent indicates that the virtual disk extent is free space;allocating a section of the virtual disk file to describe the virtualdisk extent without overwriting a preexisting bit pattern within thesection of the virtual disk file; modifying the state informationassociated with the virtual disk extent to indicate that the virtualdisk extent is mapped to the allocated section of the virtual disk file;and storing the data to the allocated section of the virtual disk file.18. The method of claim 17, further comprising dissociating the virtualdisk extent from the virtual disk file and modifying the stateinformation associated with the virtual disk extent to indicate that thevirtual disk extent has been zeroed in response to determining that thevirtual disk extent was zeroed.
 19. The method of claim 17, furthercomprising dissociating the virtual disk extent from the virtual diskfile and modifying the state information associated with the virtualdisk extent to indicate that the virtual disk extent includes arbitrarydata in response to receipt of a signal from a file system identifyingthe virtual disk extent as free space.
 20. The method of claim 17,further comprising dissociating the virtual disk extent from the virtualdisk file and modifying the state information associated with thevirtual disk extent to indicate that the virtual disk extent includes anon-information disclosing bit pattern in response to receipt of arequest to trim all the sectors of the virtual disk extent.